正数的错误代码
0 Success.
The operation succeeded. The database server returns this SQLCODE value to an application when an SQL statement executes successfully.
操作成功了。当 SQL 语句成功执行时，数据库服务器将此 SQLCODE 值返回给应用程序。
100 No matching records found.
The database server did not find any more data. This message is an ANSI-standard SQLCODE value. If you attempted to select or fetch data, you encountered the end of the data, or no data matched the criteria in the WHERE clause. Check for an empty table. Use this SQLCODE value to determine when a statement reaches the end of the data. For more information, see the discussion of SQLCODE in the GBase 8s ESQL/C Programmer's Manual. The database server can return this SQLCODE value to a running program.
数据库服务器没有找到更多的数据。此消息是 ANSI 标准的 SQLCODE 值。如果试图选择或获取数据，您将会遇到数据的结尾，或者没有任何数据与 WHERE 子句中的条件匹配。
检查一下空表。使用此 SQLCODE 值确定语句何时到达数据末尾。有关更多信息，请参见GBase 8s ESQL/C 程序员手册中 SQLCODE 的讨论。数据库服务器可以将此 SQLCODE值返回给正在运行的程序。
For the High-Performance Loader (HPL), this message can indicate that the map might be from a project other than the default project. Use the -p option in the onpload command line to provide a project name for mappings.
对于高性能装载机（HPL），此消息可以指示映射可能来自缺省项目以外的项目。使用onpload 命令行中的 -p 选项为映射提供项目名称。
1203 Cannot find message file.
DataExtract cannot locate a needed message file. Check that you specified the appropriate pathname when you set the GBS_DATA and DBLANG environment variables. Contact your system administrator if you need help setting these environment variables.
DataExtract 无法找到所需的消息文件。在设置 GBS_DATA 和 DBLANG 环境变量时检查是否指定了适当的路径名。如果需要帮助设置这些环境变量，请与系统管理员联系。
1204 Your system encountered an unknown type of terminal.
Check that you set the TERM environment variable correctly. Check the database name for correct spelling. Contact your system administrator if you need help setting the environment variable.
检查是否正确设置了 TERM 环境变量。检查数据库名称是否正确拼写。如果需要帮助设置环境变量，请与系统管理员联系。
2005 Database database-name not found or not correct format.
Check the database name for correct spelling.
检查数据库名称是否正确拼写。
2008 The table table-name does not exist in the database.
The database that is specified in the DATABASE section does not contain the table name that is included in the TABLE section of the form specification file. Check the table name for correct spelling.
DATABASE 部分中指定的数据库不包含表单规范文件的 TABLE 部分中包含的表名。检查表名是否正确拼写。
2009 You did not select any database tables.
You must include one or more table names in the TABLES section of the form-specification file.
必须在表单规范文件的 TABLES 部分中包含一个或多个表名。
2020 The following tables are involved in an error: table-name.
Check the accompanying message for an indication of system action. The specified error involves the indicated tables.
检查所附消息以获得系统操作的指示。指定的错误涉及指定的表。
4074 Cannot find a C language compiler in any directory in your path.
For this 4GL compiler message, you need a C compiler to finish compiling your program. Change your execution path so that a C compiler can be executed under the name cc.
对于这条 4GL 编译器消息，您需要一个 C 编译器来完成编译您的程序。更改您的执行路径，以便 C 编译器可以在名称 cc 下执行。
4102 See error number -number.
For this 4GL compiler message, look up the message for -number.
对于这个 4GL 运行时错误，请检查编号的消息。
4150 Program error at module, line number line.
The indicated line contains incorrect code that generated this 4GL runtime message. Sometimes the actual error or omission exists in the preceding lines of code. Look for additional messages that explain the error.
指定的行包含生成此 4GL 运行时消息的不正确代码。有时实际的错误或遗漏存在于前面的代码行中。查找解释错误的其他消息。
4152 FORMS statement error number -number.
For this 4GL runtime error, check the message for -number.
对于这个 4GL 运行时错误，请检查 -number 的消息。
4153 SQL statement error number -number.
For this 4GL runtime error, check the message for -number.
对于这个 4GL 运行时错误，请检查 -number 的消息。
4154 Program stopped at module, line number line.
This 4GL runtime message tells where a program stopped due to an error. Look for additional messages that explain the error.
此 4GL 运行时消息指示程序因错误而停止的位置。查找解释错误的其他消息。
4155 4GL run-time error number -number.
For this 4GL runtime error, check the message for -number.
对于这个 4GL 运行时错误，请检查 -number 的消息。
4156 ISAM error number -number.
For this 4GL runtime error, check the message for -number.
对于这个 4GL 运行时错误，请检查 -number 的消息。
4157 SYSTEM error number -number.
For this 4GL runtime error, check the message for -number.
对于这个 4GL 运行时错误，请检查 -number 的消息。
8009 See error number errno.
Check the accompanying message for an indication of system action. Use the finderr utility to locate the indicated error message.
检查所附消息以获得系统操作的指示。使用 finderr 实用程序定位指定的错误消息。
12750 db <database_name>, tabid <table_identifier>: Must alter raw table to standard.
To change the logging TYPE option of each table from RAW to STANDARD, use the ALTER TABLE statement. After altering the tables to STANDARD, you can revert the database server.
若要将每个表的日志 TYPE 选项从 RAW 更改为 STANDARD，请使用 ALTER TABLE 语句。将表更改为标准后，可以还原数据库服务器。
16755 oninit: VPCLASS VPCLASS_name duplicate class name.
The VPCLASS parameter in the onconfig file has a duplicate name. The VPCLASS name must be unique. Correct the onconfig file and restart oninit.
onconfig 文件中的 VPCLASS 参数有一个重复的名称。VPCLASS 名称必须是唯一的。更正onconfig 文件并重新启动 oninit。
16872 Logical Recovery Complete - no log replay was necessary.
During restore, the database server determined that none of the dbspaces involved had any logging activity since they were backed up.
You do not need to look through log backups on tape because nothing would be found.
在恢复过程中，数据库服务器确定所涉及的 dbspace 没有任何日志记录活动，因为它们被备份了。您不需要查看磁带上的日志备份，因为什么都找不到。
You do not need to take any action.
您不需要采取任何。
16888 Logslice successfully altered by adding logs.
Logical logs were added to all new dbspaces in the altered dbslice.
逻辑日志被添加到修改后的 dbslice 中的所有新 dbspace 中。
Perform a level-0 backup or fake backup to enable the new logical logs.
执行级别为 0 的备份或假备份，以启用新的逻辑日志。
16889 Dbslice successfully altered by adding dbspaces.
Dbspaces were added to all named coservers.
Dbspace 被添加到所有命名的 coservers 中。
You do not need to take any action.
您不需要采取任何。
19568 oninit: Too many VPCLASS parameters specified.
Too many VPCLASS parameter lines exist in the onconfig file. Reduce the number of VPCLASS lines and restart oninit.
onconfig 文件中存在太多的 VPCLASS 参数行。减少 VPCLASS 行数并重新启动 oninit。
19569 oninit: VPCLASS VPCLASS_name bad affinity specification.
The affinity specification for the VPCLASS line is incorrect. Affinity is specified as a range where x is less than or equal to z, and both x and z are greater than zero.
VPCLASS 行的关联规范是不正确的。关联被指定为一个范围，其中 x 小于或等于 z ，并且 x 和 z 都大于零。
x: use processor x x：使用处理器 x x - z: use processors in the range x to z inclusive x-z：使用 x 到 z 范围内的处理器19570 oninit: Cannot mix VPCLASS cpu and NUMCPUVPS, SINGLE_CPU_VP,AFF_SPROC, AFF_NPROCS, or NOAGE parameters.
CPU VPs can be configured using either VPCLASS CPU or the old parameters NUMCPUVPS and so on. However, CPU VPs cannot be configured by mixing both formats.
CPU VPs 可以使用 VPCLASS CPU 或旧参数 NUMCPUVPS 等进行配置。但是，不能通过混合这两种格式来配置 CPU VPs。
19571 oninit: Cannot mix VPCLASS aio and NUMAIOVPS parameters.
AIO VPs can be configured with VPCLASS AIO or the old parameter NUMAIOVPS. However, AIO VPs cannot be configured with both formats.
可以使用 VPCLASS、AIO 或旧参数 NUMAIOVPS 配置 AIO VPs。但是，AIO VPs 不能同时配置这两种格式。
19572 oninit: VPCLASS VPCLASS_name number of VPs is out of the range 0 to 10000.
The initial number of VPs specified by a VPCLASS parameter line must be in the range 0 to 10,000. Correct the onconfig file and restart oninit.
VPCLASS 参数行指定的 VPs 的初始数量必须在 0 到 10,000 之间。更正 onconfig 文件并重新启动 oninit。
19573 oninit: VPCLASS VPCLASS_name maximum number of VPs is out of the range 1-10000.
The maximum number of VPs specified by a VPCLASS parameter line must be in the range 0 to 10,000. Correct the onconfig file and restart oninit.
VPCLASS 参数行指定的最大 VP 数必须在 0 到 10，000 之间。更正 onconfig 文件并重新启动 oninit。
19574 oninit: VPCLASS VPCLASS_name number of VPs is greater than the maximum specified.
The initial number of VPs specified by a VPCLASS parameter is greater than the maximum specified by the same VPCLASS parameter. Correct the onconfig file and restart oninit.
由 VPCLASS 参数指定的 VPs 的初始数目大于同一 VPCLASS 参数指定的最大值。更正onconfig 文件并重新启动 oninit。
19575 oninit: VPCLASS VPCLASS_name bad scheduler specification.
One of the options for a VPCLASS parameter is illegal. Check your Administrator's Guide for legal values. Correct the onconfig file and restart oninit.
VPCLASS 参数的选项之一是非法的。请查看“管理员指南”中的合法值。更正 onconfig文件并重新启动 oninit。
19750 Invalid serial number. Consult your installation guide.
This RSAM error message indicates an incorrect serial number.
此 RSAM 错误消息指示不正确的序列号。
19812 Illegal use of replication shadow columns.
The specified operation cannot be performed on the replication shadow columns while replication is enabled.
在启用复制时，无法对复制阴影列执行指定的操作。
19813 Cannot add CRCOLS when the table already has replication shadow columns.
The specified table was created with the WITH CRCOLS clause and therefore already has the replication shadow columns defined. You cannot alter this table to add CRCOLS to it.
指定的表是用 WITH CRCOLS 子句创建的，因此已经定义了复制阴影列。不能更改此表以向其添加 CRCOLS。
19814 Cannot drop CRCOLS when table does not have replication shadow columns.
The specified table was not created with the WITH CRCOLS clause, or it has not been altered to include the CRCOLS. You cannot alter this table and drop the CRCOLS because these columns do not exist on this table.
指定的表不是用 WITH CRCOLS 子句创建的，也没有更改为包含 CRCOLS。您不能更改此表并删除 CRCOLS，因为此表中不存在这些列。
19815 Cannot create a temp table with CRCOLS.
You cannot create a temporary table to include the replication shadow columns. If you did not intend to name a temporary table, check the spelling of the table name.
不能创建包含复制阴影列的临时表。如果不打算命名临时表，请检查表名的拼写。
19816 Cannot perform this operation on a table defined for replication.
The specified operation cannot be performed on a table if Enterprise Replication is defined on the table. If you want to perform the specified operation, you must delete all replicates defined on this table.
如果在表上定义了 Enterprise Replication ，则无法在表上执行指定的操作。如果要执行指定的操作，必须删除此表中定义的所有副本。
If the table is being captured using the Change Data Capture interface,then you must use CDC API functions to stop data capture and disable full row logging on the table.
如果使用更改数据捕获接口捕获表，则必须使用 CDC API 函数来停止数据捕获并禁用表上的全行日志记录。
19989 Enterprise Replication is not in active state The specified operation cannot be performed on a table defined for replication if Enterprise replication is not in active state.
If you want to perform the specified operation, you must start Enterprise Replication.
如果 Enterprise Replication 未处于活动状态，则无法对为复制定义的表执行指定的操作。如果要执行指定的操作，则必须启动 Enterprise Replication 。
19991 Table is not in Enterprise Replication alter mode The specified operation cannot be performed on a table defined for replication if the table is not in Enterprise Replication alter mode.
If you want to perform the specified operation, you must put the table in Enterprise Replication alter mode.
如果表不处于 Enterprise Replication 修改模式，则无法对为复制定义的表执行指定的操作。如果要执行指定的操作，则必须将表置于 Enterprise Replication 修改修改模式。
19992 Cannot perform insert/delete/update operations on a replicated table while the table is in alter mode The specified operation cannot be performed on a table defined for replication if the table is in Enterprise Replication alter mode.
If you want to perform the specified operation, you must unset the Enterprise Replication alter mode.
如果表处于 Enterprise Replication 修改模式，则无法对为复制定义的表执行指定的操作。如果要执行指定的操作，则必须取消设置 Enterprise Replication 修改模式。
19993 Cannot modify a replicated column The specified operation cannot be performed on a table defined for replication. If you want to perform the specified operation,you must remove the column from the replicate definition, alter the column then add the column again to the replicate definition through Enterprise Replication remastering process.
不能在为复制定义的表上执行指定的操作。如果要执行指定的操作，则必须从复制定义中移除该列，然后更改该列，然后通过 Enterprise Replication remastering 过程将该列再次添加到复制定义中。
19994 Cannot drop a replicated column while the column is part of replicate definition The specified operation cannot be performed on a table defined for replication. If you want to perform the specified operation,you must remove the column from the replicate definition through Enterprise Replication remastering process.
不能在为复制定义的表上执行指定的操作。如果要执行指定的操作，则必须通过Enterprise Replication remastering 过程从复制定义中删除该列。
19995 Enterprise Replication error encountered while setting alter mode. See the message log file to get the Enterprise Replication error code.
Enterprise Replication error encountered while performing the specified operation. See the message log file to get the Enterprise replication error code. If you want to perform the specified operation, correct the Enterprise Replication problem and reattempt the operation.
执行指定的操作。查看消息日志文件以获取 Enterprise Replication 错误代码。如果要执行指定的操作，纠正 Enterprise Replication 问题然后再试一次操作。
19996 Enterprise Replication error encountered while unsetting alter mode.
See message log file to get the Enterprise Replication error code Enterprise Replication error encountered while performing the specified operation. See the message log file to get the Enterprise replication error code. Correct the problem and clear the alter mode manually through cdr command line utility.
执行特定操作时遇到的 Enterprise Replication 错误。请参阅消息日志文件以获取Enterprise Replication 错误代码。通过 cdr 命令行实用程序纠正问题并手动清除修改模式。
19820 GBase 8s OUTER JOIN and ANSI JOIN in the same query block.
You cannot have GBase 8s OUTER JOIN and ANSI JOIN in the same query block. GBase 8s OUTER JOIN and ANSI JOIN are two different mechanisms and should not be combined in a single query. You can use only one of these.
不能在同一个查询块中使用 GBase 8s 外部联接和 ANSI 连接。GBase 8s 外部联接和ANSI 连接是两种不同的机制，不应该在一个查询中组合。你只能用其中一个。
19821 Cannot rename a table using a synonym.
You cannot use a synonym to perform a rename operation. Specify the
不能使用同义词执行重命名操作。指定
To rename the synonym, drop the existing synonym and create a new one.
若要重命名同义词，请删除现有的同义词并创建一个新的同义词。
19822 Cannot alter or truncate a table or drop a table or view using a synonym.
You cannot use a synonym to perform an alter or truncate or drop on a table or a view.
Specify the
不能使用同义词在表或视图上执行修改或清空或删除。
指定
To drop the table or view or alter or truncate the table using the synonym,unset the environment variable USETABLENAME.
若要使用同义词删除表或视图或更改或清空表，请取消设置环境变量 USETABLENAME 。
To drop the synonym and not the table or view, specify DROP SYNONYM
若要删除同义词而不是表或视图，请指定 DROP SYNONYM
19823 Cannot use EXECUTE PROCEDURE INTO with the INSTEAD OF trigger.
You cannot use EXECUTE PROCEDURE INTO with the INSTEAD OF trigger.
不能将 EXECUTE PROCEDURE INTO 和替换触发器一起使用。
19824 Cannot use BEFORE or AFTER action with the INSTEAD OF trigger.
You cannot use the BEFORE or AFTER actions with the INSTEAD OF trigger. You must use the FOR EACH ROW action with the INSTEAD OF trigger.
不能将“ BEFORE ”或“ AFTER ”操作与“ INSTEAD OF ”一起使用。必须将“用于每行”操作与“替换触发器”一起使用。
19825 Cannot use WHEN clause if INSTEAD OF trigger is defined.
You cannot use the WHEN clause to restrict the triggered action in INSTEAD OF trigger definitions. The action of the triggering statement is always replaced by the specified triggered action on the base table(or tables) of the view on which the INSTEAD OF trigger is defined.
在替换触发器定义中不能使用 WHEN 子句来限制触发操作。触发器语句的操作总是在定义了 INSTEAD OF 触发器的视图的基表（或表）上被指定的触发操作所替换。
19826 Cannot create INSTEAD OF trigger for a select event.
You can create an INSTEAD OF trigger for an insert, update, or delete event, but not for a select event.
可以为 INSERT 、UPDATE 或 DELETE 事件创建 INSTEAD OF 触发器，但不能为 SELECT 事件创建触发器。
19827 Cannot create an INSTEAD OF trigger on a table.
You can only create an INSTEAD OF trigger on a view, not on a base table or synonym.
您只能在视图上创建 INSTEAD OF 触发器，而不能在基表或同义词上创建。
21957 Invalid block size.
You have specified inadequate block size for the tape device in your onload or onunload command. Make the block size larger than the size(in kilobytes) that the accompanying error message indicates. The onload and onunload utilities require a block-size parameter with a minimum value of 4 for 2-kilobyte-page computers or 8 for 4-kilobyte-page computers.
您已在 onload 或 onunload 命令中为磁带设备指定了不适当的块大小。使块大小大于所附错误消息指示的大小（以千字节为单位）。onload 和 onunload 实用程序需要一个块大小参数，最小值为 2 KB 页计算机为 4，对于 4 KB 页计算机为 8。
25500 The sqlexecd daemon is not licensed for remote use.
You entered an incorrect serial number or serial-number key while you were running the GBase 8s client/server product installation script.
Obtain the proper serial number and key and reinstall your GBase 8s client/server product.
在运行 GBase 8s 客户机/服务器产品安装脚本时，输入了错误的序列号或序列号密钥。
获取适当的序列号和密钥，然后重新安装 GBase 8s 客户机/服务器产品。
25501 You must log in as root to start the sqlexecd daemon.
Log in as root and start the sqlexecd daemon process.
以 root 身份登录并启动 sqlexecd 守护进程。
25502 The sqlexecd daemon cannot execute the fork system call.
Contact your system administrator to solve system problems.
与系统管理员联系解决系统问题。
25503 GBase 8s network features not supported on this product.
The sqlexecd daemon does not support your network connections. Check that you specified the correct database or database server in the DBPATH environment variable. Consult your system administrator about GBase 8s NET licensing issues.
sqlexecd 守护进程不支持您的网络连接。检查是否在 DBPATH 环境变量中指定了正确的数据库或数据库服务器。有关 GBase 8s NET 许可问题，请咨询系统管理员。
25504 The sqlexecd daemon cannot open a socket.
Check that you correctly installed the TCP/IP network. Check for malfunctions in the TCP/IP network.
检查是否正确安装了 TCP/IP 网络。检查 TCP/IP 网络中的故障。
25505 The sqlexecd daemon cannot bind a name to the socket.
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25506 The sqlexecd daemon cannot accept a connection on the socket.
Check that you correctly installed the TCP/IP network. Check for malfunctions in the TCP/IP network.
检查是否正确安装了 TCP/IP 网络。检查 TCP/IP 网络中的故障。
-25507 You specified an unknown service name or protocol.
Determine which of the following conditions produced this error and take the appropriate corrective actions:确定下列哪一种条件造成了这一错误，并采取适当的纠正措施：The value of the NETTYPE configuration parameter in the ONCONFIG file is not the same as the NETTYPE setting in the sqlhosts file. If the NETTYPE values are different, correct the incorrect value. If you update the ONCONFIG file,you must restart the database server.
ONCONFIG 文件中的 NETTYPE 配置参数的值与 sqlhost 文件中的 NETTYPE 设置不相同。
如果 NETTYPE 值不同，请更正不正确的值。如果更新 ONCONFIG 文件，则必须重新启动数据库服务器。
The correct service name is not in the /etc/services file. If you are using the TCP/IP protocol, check the /etc/services file. If you are using NFS, use the ypmake utility to check the /etc/services file. Sometimes the daemon does not recognize service names that are added after a default start-up. Add the correct service name if it is not present or restart your computer.
正确的服务名称不在 /etc/services 文件中。如果使用 TCP/IP 协议，请检查/etc/services 文件。如果使用 NFS，请使用 ypmake 实用程序检查 /etc/services 文件。有时，守护进程不识别在缺省启动后添加的服务名称。如果不存在或重新启动计算机，则添加正确的服务名称。
The protocol entry in the ONCONFIG file or sqlhosts file is not supported by the operating system on your computer. For information about supported protocols, see the connectivity information section in the Administrator's Guide. Correct the protocol entry in the ONCONFIG file or the sqlhosts file. If you update the ONCONFIG file, you must restart the database server.
计算机上的操作系统不支持 ONCONFIG 文件或 sqlhost 文件中的协议条目。有关支持的协议的信息，请参阅管理员指南中的连接信息部分。更正 ONCONFIG 文件或 sqlhost 文件中的协议条目。如果更新 ONCONFIG 文件，则必须重新启动数据库服务器。
25510 execv could not start the database engine
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25511 The sqlexecd daemon could not receive data from client.
Check that you correctly installed the TCP/IP network. Check for malfunctions in the TCP/IP network.
检查是否正确安装了 TCP/IP 网络。检查 TCP/IP 网络中的故障。
25512 Cannot access the database server program.
Check that you can access the requested database server program.
检查是否可以访问请求的数据库服务器程序。
25514 The sqlexecd daemon cannot open the log file.
Check that you can write to the requested log file.
检查是否可以写入请求的日志文件。
25515 You passed too many arguments to the sqlexecd daemon.
Refer to your GBase 8s product manuals. Check the version information that is associated with your GBase 8s client/server products to verify compatibility between those products.
请参阅您的 GBase 8s 产品手册。检查与 GBase 8s 客户机/服务器产品关联的版本信息，以验证这些产品之间的兼容性。
25518 You specified an unknown network type in DBNETTYPE. Assuming STARLAN.
If your network supports STARLAN connections, set the DBNETTYPE environment variable to starlan. If your network supports TCP/IP connections, set the DBNETTYPE environment variable to tcp/ip.
如果您的网络支持 STARLAN 连接，则将 DBNETTYPE 环境变量设置为 starlan 。如果您的网络支持 TCP/IP 连接，则将 DBNETTYPE 环境变量设置为 TCP/IP 。
25519 The sqlexecd daemon cannot open the network device.
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25520 The sqlexecd daemon cannot allocate the call structure.
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25521 The sqlexecd daemon cannot allocate the return structure.
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25522 The sqlexecd daemon cannot allocate the call structure.
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25523 The sqlexecd daemon cannot bind the network structures.
The sqlexecd daemon process attempted to use the same service number that is allocated to another running process. Check that the system administrator does not need to use the running sqlexecd process, and then stop the sqlexecd process, and start a new one. Or add a new entry to the /etc/services file, and start a daemon for the service using the new service number. For more information, refer to your system manual.
sqlexecd 守护进程试图使用分配给另一个正在运行的进程的相同服务号。检查系统管理员是否不需要使用正在运行的 sqlexecd 进程，然后停止 sqlexecd 进程，并启动一个新进程。或者向 /etc/services 文件添加一个新条目，并使用新的服务号启动服务的守护进程。有关详细信息，请参阅系统手册。
25526 The sqlexecd daemon cannot listen on the network device.
Enter your request again. If the problem persists, run your network diagnostics to determine the source of the problem.
再次输入你的请求。如果问题仍然存在，请运行网络诊断以确定问题的来源。
25528 The sqlexecd daemon cannot accept a connection.
Check that you correctly installed your network hardware and software.
Check for malfunctions in the network.
检查是否正确安装了网络硬件和软件。检查网络中的故障。
25529 The sqlexecd daemon cannot get a host structure.
Check that you requested a valid host name. Verify that the /etc/hosts file contains the requested host-name entry.
检查您是否请求了一个有效的主机名。验证 /etc/host 文件是否包含请求的主机名条目。
25530 The sqlexecd daemon cannot bind to the required port address.
Check that no other daemons are running on the port address.
检查端口地址上是否没有运行其他守护进程。
25531 The sqlexecd daemon cannot bind to the required address.
Check that no other daemons are running on the port address.
检查端口地址上是否没有运行其他守护进程。
25533 The sqlexecd daemon cannot close the network.
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25534 The sqlexecd daemon cannot allocate a structure.
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25535 Address translation failed in sqlexecd daemon.
Enter your request again. If the problem persists, refer to your system manual for more information.
再次输入你的请求。如果问题仍然存在，请参阅系统手册以获得更多信息。
25537 The sqlexecd daemon cannot connect to network.
Check that you correctly installed your TCP/IP or StarGROUP network.
Check for malfunctions in the network.
检查是否正确安装了 TCP/IP 或 StarGROUP 网络。检查网络中的故障。
25543 You specified an unknown service name or protocol.
Examine the /etc/services file to verify that the requested service name exists. Also check that the /etc/services file specifies the correct protocol and/or port number.
检查 /etc/services 文件，以验证请求的服务名称是否存在。还要检查 /etc/services文件是否指定了正确的协议和/或端口号。
25544 The sqlexecd daemon cannot find a host structure.
Check that you requested a valid database server name. Examine the /etc/hosts file to verify that you correctly defined the requested database server name,client address, and host names.
检查是否请求了有效的数据库服务器名称。检查 /etc/host 文件，以验证您是否正确定义了请求的数据库服务器名称、客户端地址和主机名。
25545 The sqlexecd daemon cannot advertise the specified service name.
You are starting the sqlexecd daemon on a system that is running portable GBase 8s OnLine for NetWare with IPX/SPX as the network protocol, but the daemon is unable to advertise the service name for the database server on the NetWare network. It is possible that another sqlexecd daemon is already using the same service name, a recently stopped sqlexecd daemon with the same service name was unable to de-advertise its service, or the database server is down.
您将在一个运行 GBase 8s OnLine 用于 NetWare 的系统上启动 sqlexecd 守护进程，该系统以 IPX/SPX 作为网络协议，但守护进程无法为 NetWare 网络上的数据库服务器发布服务名称。可能另一个 sqlexecd 守护进程已经使用了相同的服务名称，最近停止了具有相同服务名称的 sqlexecd 守护进程，无法取消发布其服务，或者数据库服务器停机。
The service name of each database server must be unique across the entire NetWare network. The default service name is sqlexec. If another sqlexecd daemon or database server on the network already uses the name, use a different service name to start the sqlexecd daemon.
You can explicitly specify a service name as a parameter in the sqlexecd command line.
在整个 NetWare 网络中，每个数据库服务器的服务名称必须是唯一的。缺省的服务名称是 sqlexec。如果网络上的另一个 sqlexecd 守护进程或数据库服务器已经使用了该名称，则使用不同的服务名称来启动 sqlexecd 守护进程。您可以显式地指定服务名称作为sqlexecd 命令行中的参数。
If you are restarting a recently terminated sqlexecd daemon, the previous sqlexecd probably has not finished de-advertising or was unable to de-advertise the service name. When you terminate an sqlexecd daemon, use the TERM signal (15) only (that is, kill -15 pid or kill pid). If you do not terminate a service properly, depending on your database server configuration, it might take about three minutes for a terminated service to be de-advertised automatically.
如果您正在重新启动最近终止的 sqlexecd 守护进程，则以前的 sqlexecd 可能还没有完成取消发布，或者无法取消该服务名称的发布。当您终止 sqlexecd 守护进程时，只使用TERM Signal(15) （也就是说，kill -15 pid 或 kill pid）。如果您没有正确地终止服务，这取决于您的数据库服务器配置，终止的服务可能需要大约三分钟的时间才能自动取消发布。
29061 EDA warning (EDA_warning).
The SQL statement has executed successfully, but the EDA client or server issued a warning. The EDA_warning field contains the warning information.
SQL 语句已成功执行，但 EDA 客户端或服务器发出警告。EDA_warning 字段包含警告信息。
The format of the EDA_warning field is the same as for the EDA_Error field that is described for error message -29060.
EDA_warning 字段的格式与为错误消息 -29060 描述的 EDA_Error 字段的格式相同。
32700 Cannot find license file.
The program cannot open the license file. It first tries to open the file that the user specified in LM_LICENSE_FILE. If you have not set this environment variable, the program tries to open the license file in the default location $GBS_HOME/etc/ifmxld.dat. If you intend to use LM_LICENSE_FILE, check that you have set your license-file pathname correctly in that file.
程序无法打开许可证文件。它首先尝试打开用户在 LM_LICENSE_FILE 文件中指定的文件。如果尚未设置此环境变量，程序尝试在缺省位置 $GBS_HOME/etc/ifmxld.dat中打开许可证文件。如果您打算使用 LM_LICENSE_FILE 文件，请检查您在该文件中正确设置了许可证文件路径名。
32701 Invalid license file syntax.
This error occurs if the feature name, daemon name, or server name exceeds the maximum length allowed, or if the feature line is incomplete. If you have edited the license file after installation,check that you did not make a mistake. The maximum length for the server name is 32 characters. The feature name, daemon name, and feature lines are generated automatically during installation.
如果特性名称、守护进程名称或服务器名称超出允许的最大长度，或者如果特性行不完整，则会发生此错误。如果您在安装后编辑了许可证文件，请检查您没有犯错误。服务器名称的最大长度为 32 个字符。在安装过程中自动生成特性名称、守护进程名称和特性行。
32702 Cannot connect to a license daemon server.
If you edited the license file after installation, check that you did not make a mistake. This error occurs if the daemon name specified in the license-file feature line does not match the vendor-daemon name or if the attempt to connect the vendor daemon on all server nodes was unsuccessful. Check that the daemons on all license servers are still running and that the network is working properly.
如果安装后编辑了许可文件，请检查是否出错。检查所有许可证服务器上的守护进程是否仍在运行，网络是否正常工作。
32703 Licensed number of users already reached. Check the daemon log.
Check the network-licensing activities by using lmstat or by checking the license-daemon log file to decide whether you need to purchase more user capacity from GBase.
通过使用 lmstat 或通过检查许可证守护进程日志文件来检查网络许可活动，以决定是否需要从 GBase 购买更多的用户容量。
32704 No such feature exists.
The feature could not be found in the license file. Be sure that the license file contains the feature line for the product that you are trying to use and that the product is properly licensed.
在许可证文件中找不到该特性。请确保许可证文件包含您试图使用的产品的特性行，并且该产品已获得正确的许可证。
32705 No TCP/IP license service exists.
Check the license file in use to ensure that the TCP/IP port number on the server line or lines is valid. If the TCP/IP port number is not valid, modify the license file to use a valid one.
检查正在使用的许可证文件，以确保服务器行上的 TCP/IP 端口号是有效的。如果TCP/IP 端口号无效，请修改许可证文件以使用有效文件。
32706 No socket connection to license manager server.
This error indicates that an internal error occurred during sending or receiving of the message. Note all observed behavior and any other error message. Check with the system administrator to ensure that the system is functioning properly.
此错误表示在发送或接收消息期间发生内部错误。注意所有观察到的行为和任何其他错误消息。与系统管理员联系，确保系统正常运行。
32707 Encryption code in license file is inconsistent.
This error indicates that the code in a license-file line does not match the other data in the license file. This error usually occurs when all the software components are not built with the same encryption code. Check create_license.c, ls_vendor.c, and your application code carefully to make sure that they have the same vendor code. Do not modify the encryption code in the license file after it has been generated during installation.
此错误表示许可证文件行中的代码与许可证文件中的其他数据不匹配。当所有软件组件都不是使用相同的加密代码构建时，通常会发生此错误。请仔细检查create_license.c、ls_vendor.c 和您的应用程序代码，以确保它们具有相同的供应商代码。安装过程中生成许可证文件后，不要修改许可证文件中的加密代码。
32708 Invalid host.
This error occurs when the host ID specified in the license file does not match the node on which the software is running.
当许可证文件中指定的主机 ID 与运行软件的节点不匹配时，会发生此错误。
32709 Feature has expired.
The present date exceeds the expiration date of the feature in the license file. Decide if you want to change from an evaluation version to a regular version of this GBase 8s product and contact GBase for the procedure that you need.
当前日期超过许可证文件中的特性的过期日期。决定是否要从评估版本更改为 GBase 8s产品的常规版本，并与 GBase 联系以获得所需的程序。
32710 Invalid date format in license file.
Check that the date field in the license file is in the format dd-mmm-yyyy where dd is two digits for the day, mmm is three letters for the month, and yyyy is four digits for the year. The installation procedure generates these dates. If you did not modify the license file on those fields, report this problem, along with the output of the license file, to GBase Technical Support.
检查许可证文件中的 Date 字段在 dd-mmm-yyyy 格式中，其中 dd 为两位数字表示天，mmm 为三个字母表示月份，yyyy 为四位数字表示年。安装过程生成这些日期。
32711 Invalid returned data from license daemon server.
Be sure that no other services use the port numbers on the server lines. Check with your system administrator to ensure that the network is functioning properly. Check the license-daemon-server log for all error messages.
确保没有其他服务使用服务器线路上的端口号。与系统管理员联系，确保网络正常运行。
检查许可证-守护进程-服务器日志中的所有错误消息。
32712 No server lines in license file.
No server line exists in the license file. All nonzero license-count features need at least one server line.
许可证文件中不存在服务器行。所有非零许可证计数功能至少需要一行服务器行。
32713 Cannot find SERVER hostname in network database.
Check all relevant system files, such as /etc/hosts, to ensure that the server host name is known across the network.
检查所有相关的系统文件，例如 /etc/host，以确保服务器主机名在网络中被知道。
32714 Cannot read data from license daemon server.
Be sure that the daemons in all license servers are running. Check the daemon log for any error message.
确保所有许可证服务器中的守护进程都在运行。检查守护进程日志中是否有任何错误消息。
32715 Cannot write data to license daemon server.
Check with your system administrator to ensure that the network is functioning properly. Also check the daemon log for other error messages.
请与系统管理员联系，以确保网络正常运行。还要检查守护进程日志是否有其他错误消息。
32716 License daemon server does not support this feature.
The feature has expired or has not yet started, or the version of the product you are attempting to use is not the licensed version. Check that the license files in both the license-daemon servers and the computer that is running this GBase 8s licensed product are set up properly.
该功能已经过期或尚未启动，或者您试图使用的产品的版本不是授权版本。检查许可守护进程服务器和运行此 GBase 8s 许可产品的计算机中的许可证文件是否正确设置。
32717 License daemon server busy (no majority).
The license-daemon server is busy establishing a quorum of server nodes so that licensing can start. Retry this operation later.
许可证守护进程服务器正忙着建立服务器节点的仲裁，以便许可可以启动。稍后重试此操作。
32718 License file does not support this version.
Be sure that the version of the product that you are attempting to use is licensed. Check the license file to ensure that the version of the desired product on the feature line is the same as or later than the version that you want to use.
确保您试图使用的产品的版本是被许可的。检查许可证文件，以确保功能线上所需产品的版本与您想要使用的版本相同或更晚。
32719 Feature checkin failure detected at license daemon server.
The check-in request did not receive a proper reply from the vendor daemon. (The license might still be considered in use.) Check the daemon log output to see if there are any more error messages. If the error recurs, note all circumstances and contact GBase Technical Support.
Check-in 请求没有从供应商守护进程收到正确的答复。（许可证可能仍在使用中。）检查守护进程日志输出，看看是否还有其他错误消息。如果错误再次发生，请记录所有情况并联系 GBase 8s 技术支持部门。
32720 License daemon server temporarily busy (new server connecting).
The vendor daemon is busy establishing a quorum condition. New requests from clients are deferred during this period. Retry this operation later.
供应商守护进程正忙于建立仲裁条件。客户的新请求在此期间被推迟。稍后重试此操作。
32721 License daemon server does not support this version of this feature.
The version that you are attempting to use is more recent than the version for which you are licensed. Check the feature line in the license file to ensure that the version of the desired product is the same as or later than the version that you are trying to use.
您尝试使用的版本比您获得许可的版本要新得多。检查许可证文件中的特性行，以确保所需产品的版本与您试图使用的版本相同或更晚。
32722 Request for more licenses than this feature supports.
A checkout request was made for more licenses than are supported in the license file. Be sure that you did not make a change to the license checkout request to check out more licenses than it is capable of handling. Check out only one license for each request.
对于比许可证文件中支持的更多的许可证，提出了 checkout 请求。请确保您没有更改许可证 checkout 请求，以 checkout 比它能够处理的更多的许可证。每个请求只检出一个许可证。
32723 Cannot read license file.
Be sure that the license file has the correct read permission.
确保许可证文件具有正确的读取权限。
32724 Bad encryption handshake with daemon.
The client performs an encryption handshake operation with the daemon before any licensing operations can occur. This handshake operation failed. Check with the system administrator to ensure that the system and the network are working properly. If the error recurs, note all circumstances and contact GBase Technical Support.
客户端在任何许可操作发生之前都会对守护进程执行加密握手操作。此握手操作失败。与系统管理员联系，确保系统和网络正常工作。如果错误再次发生，请注意所有情况，并与GBase 技术支持部门联系。
32725 Feature database corrupted in daemon.
The runtime-feature data structures of the daemon are corrupt. This internal daemon error indicates that a serious problem exists. If the error recurs, note all circumstances and contact GBase Technical Support.
守护进程的运行时特性数据结构已损坏。此内部守护进程错误表示存在严重问题。如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。
32726 Cannot allocate dynamic memory.
The malloc() call failed to return sufficient memory. This error can occur while the system is reading the features from the license file(especially if the user has set an extremely long LM_LICENSE_FILE path).
Check with your system administrator to ensure that the system is working properly.
malloc() 调用未能返回足够的内存。当系统从许可文件中读取特性时(特别是当用户设置了非常长的 LM_LICENSE_FILE 路径时)，可能会发生此错误。与系统管理员联系，确保系统正常工作。
32727 Feature was never checked out.
This message provides information to the user. It is not an error.
此消息向用户提供信息。这不是错误。
32728 Clock setting check not available in daemon.
This message provides information to the user. It is not an error.
此消息向用户提供信息。这不是错误。
32766 Unknown error message number.
The program that you have started cannot locate the GBase 8s error message file. The GBS_DATA environment variable is probably not set properly. GBS_HOME points to the directory that contains the msg directory where message files are stored.
您已启动的程序无法找到 GBase 8s 错误消息文件。GBS_DATA 环境变量可能没有正确设置。GBS_DATA 指向存储消息文件的 msg 目录。
32788 Dbspaces added to a mirrored Dbslice must be mirrored.
The database administrator attempted to add dbspaces to an existing mirrored dbslice by using the ALTER DBSLICE ADD DBSPACE command without the MIRROR clause for each chunk.
数据库管理员试图使用 ALTER DBSLICE ADD DBSPACE 命令将 dbspace 添加到现有的镜像dbslice 中，而不为每个 chunk 添加 MIRROR 子句。
Reissue the ALTER DBSLICE ADD DBSPACE command with the MIRROR clause for each chunk.
为每个 chunk 重新发出 ALTER DBSLICE ADD DBSPACE 命令和 MIRROR 子句。
32789 Dbspaces added to a non-mirrored Dbslice must not be mirrored.
The database administrator attempted to add dbspaces to an existing unmirrored dbslice by using the ALTER DBSLICE ADD DBSPACE command with at least one MIRROR clause for a chunk.
数据库管理员试图通过使用 ALTER DBSLICE ADD DBSPACE 命令将 dbspace 添加到现有的未镜像的 dbslice 中，至少对 chunk 使用一个 MIRROR 子句。
Reissue the ALTER DBSLICE ADD DBSPACE command without the MIRROR clause for each chunk.
在没有针对每个 chunk 的 MIRROR 子句的情况下，重新发出 ALTER DBSLICE ADD DBSPACE 命令。
32792 Coservers successfully blocked.
The EBR BLOCK command completed successfully.
EBR BLOCK 命令已成功完成。
32793 Coservers successfully unblocked.
The EBR UNBLOCK command completed successfully.
EBR UNBLOCK 命令已成功完成。
33987 External Space successfully created.
The onspaces command that you used to create the external space was successful.
用于创建外部空间的 onspace 命令成功。
33988 External space creation failed.
The database server could not add the external space. Check the error returned with this failure.
数据库服务器无法添加外部空间。检查此故障返回的错误。
33989 External Space successfully dropped.
The onspaces command that you used to drop the external space was successful.
您用来删除外部空间的 onspace 命令是成功的。
33990 External space drop fails.
An attempt to drop the external space failed. Check the error associated with this failure.
图删除外部空间的尝试失败。检查错误与这次失败有关。
33991 External Space reference count not zero. Drop fails.
The reference count for this external space was not 0. Check the reference count for the external space before you attempt to drop the space.
此外部空间的引用计数不是 0。检查尝试删除该空间之前，外部空间的引用计数。
33992 onmode: Unknown option argument.
Unknown argument passed to onmode. Retry with the correct argument list.
未知参数传递给 onmode。使用正确的参数列表重试。
35201 SQLCODE used in SQL statement or declared as IN parameter.
Remove SQLCODE from the SQL statement and/or remove IN from the parameter list. SQLCODE is an out parameter only.
从 SQL 语句中删除 SQLCODE 和/或从参数列表中删除 IN。SQLCODE 仅是 OUT 参数。
35202 SQLCODE parameter must be declared with type SQLCODE_TYPE.
Only declare SQLCODE as an SQLCODE_TYPE parameter.
只将 SQLCODE 声明为 SQLCODE_TYPE 参数。
35579 General Table Manager: Invalid argument.
An invalid argument was passed while you were attempting to create a table. If this internal error recurs, note all circumstances and contact GBase Technical Support.
在尝试创建表时传递了一个无效的参数。如果这个内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。
35580 General Table Manager: No table allocated.
The table has not been created or was deleted. If this internal error recurs, note all circumstances and contact GBase Technical Support.
表尚未创建或删除。如果这个内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。
35581 General Table Manager: No memory.
Allocation of memory for a table or a table entry failed. Try to decrease the amount of memory that is used so some memory is freed for the table or table entry.
表或表条目的内存分配失败。试着减少使用的内存量，以便为表或表条目释放一些内存。
35582 General Table Manager: Mutex cannot be created.
Table or entry mutexes cannot be created. Try to decrease the amount of memory that is used so some memory is freed for the creation of the mutex.
无法创建表或条目互斥。尽量减少使用的内存量，以便释放一些内存用于创建互斥。
35583 General Table Manager: Duplicate keys not allowed.
Table entries with the same key are not allowed. If this internal error recurs, note all circumstances and contact GBase Technical Support.
不允许具有相同键的表条目。如果这个内部错误再次出现，请注意所有情况，并与 GBase技术支持部门联系。
35584 General Table Manager: Table is full.
Table is full and cannot be extended. If this internal error recurs,note all circumstances and contact GBase Technical Support.
表已满，无法扩展。如果这个内部错误再次出现，注意所有情况，并与 GBase 技术支持部门联系。
35585 General Table Manager: Entry is locked.
Entry of a table is already locked (not yet used). If this internal error recurs, note all circumstances and contact GBase Technical Support.
表的条目已经锁定（尚未使用）。如果这个内部错误再次出现，请注意所有情况，并与GBase 技术支持部门联系。
35586 General Table Manager: Table is locked.
Table is already locked (not yet used). If this internal error recurs,note all circumstances and contact GBase Technical Support.
表的条目已经锁定（尚未使用）。如果这个内部错误再次出现，请注意所有情况，并与GBase 技术支持部门联系。
35587 General Table Manager: No entry.
The required entry does not exist. If this internal error recurs,note all circumstances and contact GBase Technical Support.
不存在所需的条目。如果这个内部错误再次出现，注意所有情况，并与 GBase 技术支持部门联系。
35588 General Table Manager: Invalid entry specification.
The specification of an entry is invalid (for example, a NULL pointer).
If this internal error recurs, note all circumstances and contact GBase Technical Support.
条目的规范无效（例如，空指针）。如果这个内部错误再次出现，请注意所有情况，并与GBase 技术支持部门联系。
35589 Running oninit without setuid causes use of descriptor limit.
When you run the database server in developer mode (not suid to root), this message is a reminder that the number of file descriptors available to the database server is now limited by the shell from which the database server is initialized. File descriptors are needed for accessing chunks and making network connections. If the database server runs out of file descriptors, you need to choose one of the following solutions: limit the number of connections, limit the number of chunks used, or run as root.
当您以开发人员模式（不是 suid 到 root）运行数据库服务器时，此消息提醒了数据库服务器可用的文件描述符的数量现在受到初始化数据库服务器的 shell 的限制。需要文件描述符来访问 chunk 和进行网络连接。如果数据库服务器用完文件描述符，则需要选择下列解决方案之一：限制连接数量、限制使用的 chunk 数或以 root 身份运行。
35590 You do not have the correct permission to run the database server without the -U option.
The user was not root or gbasedbt and was not in the group gbasedbt.
The only way to run the database server without permissions is with the -U option.
用户不是 root 或 gbasedbt 用户，也不是 gbasedbt 组中的用户。没有权限运行数据库服务器的唯一方法是使用 -U 选项。
35591 You must be the owner of this server to start it.
You are attempting to boot the database server but are not the owner.
Try again after you log in as the correct user.
您正在尝试引导数据库服务器，但不是所有者。以正确用户身份登录后再试一次。
35592 You are not the owner of this server.
You attempted to run onstat or onmode against a database server that you do not own.
您试图在您不拥有的数据库服务器上运行 onstat 或 onmode。
38002 Unknown event mnemonic or code event-mnemonic.
An unknown event mnemonic or code was encountered in the audit trail.
Check the event mnemonic or code, correct the command line or the load file, and try again.
在审计跟踪中遇到一个未知的事件助记符或代码。检查事件助记符或代码，更正命令行或加载文件，然后重试。
38005 Invalid path name, pathname (errcode = number).
You have specified an invalid pathname. Check your entry and try again.
您已经指定了一个无效的路径名。检查你的条目，然后再试一次。
38006 Invalid file name, filename (errcode = number).
You have specified an invalid filename. Check your entry and try again.
您已经指定了一个无效的路径名。检查你的条目，然后再试一次。
38007 No read permission on file filename.
You do not have read permission for the specified file. Check the permissions and try again.
您没有指定文件的读取权限。检查权限，然后再试一次。
38008 Cannot create file filename (errcode = number).
The specified file cannot be created. Check the path and directory permissions and try again.
无法创建指定的文件。检查路径和目录权限，然后再试一次。
38010 Internal error: Illegal use of set_msg (bounds exceeded).
The set_msg function has exceeded the allocated storage in the error buffer. If the error recurs, note all circumstances and contact GBase Technical Support.
set_msg 函数已超出错误缓冲区中分配的存储空间。如果错误再次发生，请注意所有情况，并与 GBase 8s 技术支持部门联系。
38047 Invalid serial number. Consult the installation instructions.
You have entered a serial number that is not valid. Check the installation instructions for your product and try again.
您输入的序列号无效。检查产品的安装说明，然后再试一次。
38053 Bad option usage: -u required for add.
Your add command for onaudit is incomplete; you did not specify a user name. Check the usage information and try again.
您的 onaudit 的添加命令是不完整的；您没有指定用户名。检查使用信息，然后再试一次。
38054 Bad option usage: -u required for modify.
Your modify command for onaudit is incomplete; you did not specify a user name. Check the usage information and try again.
您的 onaudit 的修改命令是不完整的；您没有指定用户名。检查使用信息，然后再试一次。
38055 Unknown option '-x'.
Your command line for onaudit has incorrect or incomplete syntax. You have specified an unknown option. Check the usage information and try again.
您的 onaudit 命令行语法不正确或不完整。您指定了一个未知选项。检查使用信息，然后再试一次。
38060 Badly formatted mask/role/event definition at line line-number.
The database server failed to parse the mask/role/event definition in a load file. Edit the load file and try again.
数据库服务器无法解析加载文件中的 mask/role/event 定义，编辑加载文件然后再试一次。
38061 Actions must be the first argument to onaudit.
Your command line for onaudit has incorrect or incomplete syntax.
Actions must be the first argument. Check the usage information and try again.
您的 onaudit 命令行语法不正确或不完整。操作必须是第一个参数。请检查使用信息，然后重试。
38062 Option without required argument found.
Your command line for onaudit has incorrect or incomplete syntax. You have not included a required argument with an option. Check the usage information and try again.
您的 onaudit 命令行语法不正确或不完整。您还没有在选项中包含所需的参数。检查使用信息，然后再试一次。
38064 No more than two events sets may be defined.
Your command line for onaudit has incorrect or incomplete syntax. You have specified more than two event sets. Check the usage information and try again.
您的 onaudit 命令行语法不正确或不完整。您已经指定了两个以上的事件集。检查使用信息，然后再试一次。
38065 Unable to connect to shared memory.
Confirm that the database server is up and try again.
确认数据库服务器已启动，然后再试一次。
38083 Masks cannot be modified during a bulk operation (line line-number).
The mask that was defined in a load file already exists. Either edit the load file or delete the existing definition.
加载文件中定义的掩码已经存在。要么编辑加载文件，要么删除现有定义。
38084 OS mode auditing not supported for this platform.
The -O option is not implemented for this platform. Delete it from the command and try again.
此平台没有实现 -O 选项。从命令中删除它，然后再试一次。
38085 Cannot locate ONCONFIG file.
The database server could not locate the $GBS_DATA/conf/onconfig file, and/or ADTPATH and/or SERVERNUM is not defined.
数据库服务器无法定位 $GBS_DATA/conf/onconfig 文件，和/或 ADTPATH 和/或SERVERNUM 未定义。
38086 Badly formatted audit record found.
The audit trail traversal contains a parsing error. Check the path and directory permissions and try again.
审计跟踪遍历包含一个解析错误。检查路径和目录权限，然后再试一次。
38088 Failed to action user user-name -- error number occurred.
This general onaudit failure message could indicate that a command is incorrect or incomplete, the database is inaccessible, or the user is not gbasedbt. Check the permissions, ID, and command-line syntax, and try again.
这条一般性的 onaudit 失败消息可能表示命令不正确或不完整，数据库无法访问，或者用户不是 gbasedbt。检查权限、ID 和命令行语法，然后重试。
38089 Failed to action -- error number occurred.
This general onaudit failure message could indicate that a command is incorrect or incomplete, the database is inaccessible, or the user is not gbasedbt. Check the permissions, ID, and command-line syntax, and try again.
这条一般性的 onaudit 失败消息可能表示命令不正确或不完整，数据库无法访问，或者用户不是 gbasedbt。检查权限、ID 和命令行语法，然后重试。
38090 Skipped existing audit trail filename.
The database server could not overwrite an existing audit-trail file.
This message might appear when the database server comes up and ADTPATH holds old audit data. Remove all old audit trails.
数据库服务器无法覆盖现有的审计跟踪文件。当数据库服务器出现并且 ADTPATH 保存旧的审计数据时，可能会出现此消息。删除所有旧的审计跟踪。
38091 Audit trail creation failed for filename.
The database server could not open the next audit file because the call to aio_fopen() failed. Check that ADTPATH points to a valid directory to which the user or group gbasedbt can write.
数据库服务器无法打开下一个审计文件，因为对 aio_fopen() 的调用失败。检查ADTPATH 是否指向 gbasedbt 用户或组可以写入的有效目录。
38092 Could not open next audit file.
The database server could not open the next audit file because the call to aio_fopen() failed. Check that the ADTPATH points to a valid directory to which the user or group gbasedbt can write.
数据库服务器无法打开下一个审计文件，因为对 aio_fopen() 的调用失败。检查ADTPATH 是否指向 gbasedbt 用户或组可以写入的有效目录。
38093 GBase 8s level audit write failure (errcode = number).
The database server could not write the current audit record to the audit-trail file. Check that ADTPATH points to a valid directory to which the user or group gbasedbt can write and that space is available.
Also, check the directory and audit-trail file permissions.
数据库服务器无法将当前审计记录写入审核跟踪文件。检查 ADTPATH 是否指向 gbasedbt用户或组可以写入的有效目录，以及空间是否可用。另外，检查目录和审计跟踪文件权限。
38094 string is invalid setting for ADTERR.
The ONCONFIG file contains a bad parameter. Fix the ONCONFIG file so that the parameter is 0/1.
ONCONFIG 文件包含一个坏参数。修复 ONCONFIG 文件，使参数为 0/1。
38095 string is invalid setting for ADTMODE.
The ONCONFIG file contains a bad parameter. Fix the ONCONFIG file so that the parameter is 0/1.
ONCONFIG 文件包含一个坏参数。修复 ONCONFIG 文件，使参数为 0/1。
43007 Data required to insert a row into table_name.
An insert into this table cannot occur without the specified data.
Verify that the required data exists before you attempt another insert in this table.
在没有指定数据的情况下，对此表的插入无法实现。在尝试在该表中尝试另一个插入之前，验证所需数据是否存在。
43008 Failed to build WHERE clause for query.
Attempt to build a WHERE clause for the specified query failed. Verify that the data needed to create the WHERE clause exists.
试图为指定查询生成 WHERE 子句失败。验证创建 WHERE 子句所需的数据是否存在。
43010 Missing data for table_name.
Required data is missing. Verify that the data exists.
缺少所需的数据。验证数据是否存在。
43011 Updates to table_name primary key are not allowed.
Updating the primary key for a table is not allowed. Delete the row and then insert a new row with the new primary key.
不允许更新表的主键。删除该行，然后使用新的主键插入新行。
43012 Unable to open connection to server.
The database server is in an incorrect state. Bring the database server to the correct state. For a backup, the database server should be in online or quiescent mode. For a warm restore, the database server should be in online, quiescent, backup, or recovery mode. For a cold restore, the database server should be off-line. Use the onmode or oninit commands.
数据库服务器处于错误状态。使数据库服务器处于正确状态。对于备份，数据库服务器应该处于联机或静态模式。对于温还原，数据库服务器应该处于联机、静态、备份或恢复模式。对于冷还原，数据库服务器应该处于脱机状态.使用onmode或oninit命令。
43014 Unable to read ONCONFIG file parameters.
The ONCONFIG file is inaccessible. It might be missing or have incorrect permission values. Verify that an ONCONFIG file exists and that its permissions are correct. For details, see your Administrator's Guide.
无法访问 ONCONFIG 文件。它可能丢失或具有不正确的权限值。验证是否存在 ONCONFIG文件，并验证其权限是否正确。有关详细信息，请参阅“管理员指南”。
43015 Unable to set GBASEDBTSHMBASE.
Unable to attach to shared memory. Contact your database system administrator.
无法附加到共享内存。与数据库系统管理员联系。
43018 Must be user root or gbasedbt.
Only users root and gbasedbt and are allowed to execute ON-Bar. Log in as root or gbasedbt before you attempt the backup, restore, or database logging mode change.
只有 root 和 gbasedbt 用户被允许执行 ON-Bar 。在尝试更改备份、还原或数据库日志记录模式变更之前，以 root 或 gbasedbt 身份登录。
43036 User is not a member of the gbasedbt-admin group.
Only users listed in the gbasedbt-admin group can execute ON-Bar. Ask your system administrator to add your user name to the gbasedbt-admin group.
只有 gbasedbt-admin 组中列出的用户才能执行 ON-Bar 。请系统管理员将您的用户名添加到 gbasedbt-admin 组中。
43039 Version version_number of the XBSA shared library is not compatible with version version_number of ON-Bar.
Either GBase has not certified the XBSA shared library that the Storage Management Vendor provides, or an error occurred during installation of ON-Bar. Verify that ON-Bar was installed properly.
Verify that the XBSA library is certified.
GBase 没有认证存储管理供应商提供的 XBSA 共享库，或者在安装 Gbackuprestore 期间发生了错误。验证 ON-Bar 是否已正确安装。验证 XBSA库 是否经过认证。
43040 DB/BLOBspace dbspace_name/blobspace_name does not exist.
Verify that the storage space exists in this database server.
验证此数据库服务器中是否存在存储空间。
43043 Must restore logical logs from date_time or later.
The user wants to stop the restore at a logical log that is too early.
A storage-space backup occurred after the log that the user specified. Retry the restore up to the specified logical log or later.
用户希望在一个太早的逻辑日志上停止还原。在用户指定的日志之后发生存储空间备份。
重试还原到指定的逻辑日志或更新版本。
43047 Cannot warm restore-critical media: dbspace_name.
The user wants to stop the restore at a logical log that is too early.
A storage-space backup occurred after the log that the user specified. Retry the restore up to the specified logical log or later.
用户希望在一个太早的逻辑日志上停止还原。在用户指定的日志之后发生存储空间备份。
重试还原到指定的逻辑日志或更新版本。
71561 This command can be executed only by members of the gbasedbt-admin group.
The account under which you are logged on might not be a member of the gbasedbt-admin group. Contact your Windows system administrator.
您登录的账户可能不是 gbasedbt-admin 组的成员。与 Windows 系统管理员联系。
71562 Use the -iy option to initialize the database server.
The command-line option that was specified in the Control Panel->Services->Startup dialog box was -i. When the database server runs as a service, it does not prompt you for confirmation.
在控制面板->服务->启动对话框中指定的命令行选项是 -i 。当数据库服务器作为服务运行时，它不会提示您进行确认。
If you are sure that you want to initialize the root dbspace completely, start the database server with the -iy option instead.
如果确定要初始化 root dbspace，请使用 -iy 选项启动数据库服务器。
71563 The database server cannot access %GBS_HOME%\dbssodir or%GBS_HOME%\aaodir.
First, check access rights to path segments that lead to dbssodir and aaodir. If %GBS_HOME% is on a network drive, make sure the oninit process privileges are not altered. In addition, make sure that the AAO and DBSSO group names in the following registry key are valid:首先，检查对 dbssodir 和 aaodir的路径段的访问权限。如果 %GBS_HOME% 位于网络驱动器上，请确保 oninit 进程权限不被更改。此外，确保以下注册表项中的 AAO 和DBSSO 组名称是有效的：HKEY_LOCAL_MACHINE\SOFTWARE\Gbasedbt\OnLine\CurrentVersion\Security 71564 Warning: SYSTEM command not supported in SPL routines.
Run the system command outside of the SPL routine.
在 SPL 例程之外运行系统命令。
71565 The root dbspace is not large enough for the specified configuration.
The actual size is xxx pages, and the required size is yyy pages.
Try to free some space on the drive that contains the root dbspace and re-initialize the database server.
尝试释放包含 root dbspace 的驱动器上的一些空间，并重新初始化数据库服务器。
71566 The value specified for TAPEDEV or LTAPEDEV in the ONCONFIG file is invalid.
Specify a valid value for TAPEDEV and/or LTAPEDEV. For specific information about setting configuration parameters, see your administrator's guide.
指定 TAPEDEV 和/或 LTAPEDEV 的有效值。有关设置配置参数的具体信息，请参阅管理员指南。
71567 The database server failed to start in Recovery Mode. Check Event Log for errors.
Check the Event Log for errors from the database server and correct them.
检查事件日志中是否有来自数据库服务器的错误并更正它们。
71568 oninit: DBSERVERNAME `servername' not found under SQLHOSTS key in the Registry.
Add key into the registry. For more information, refer to your administrator's guide.
将项添加到注册表中。有关更多信息，请参阅您的助理管理员指南。
71569 The database server failed to start in Recovery Mode. Service already running.
Check the registry settings for GBASEDBTSERVER under the SQLHOSTS key.
检查 SQLHOSTS 项下 GBASEDBTSERVER 的注册表设置。
71570 System() command "
Log on again with a password and execute the SPL routine.
再次使用密码登录并执行SPL例程。
71571 Insufficient buffer size for error message.
The buffer size allocated for the error message is not sufficient. If the error recurs, note all circumstances and contact GBase Technical Support.
为错误消息分配的缓冲区大小不够。如果错误再次发生，请注意所有情况，并与 GBase技术支持部门联系。
71572 System() command in SPL routine failed.
Check the message log for more information.
有关更多信息，请查看消息日志。
79511 Warning: DB_LOCALE environment variable does not match locale of the database.
The dbaccess utility issues this message when you connect to a database that does not match the value of your $DB_LOCALE environment variable.
For more information, see the section on performing code-set conversions in the GBase 8s GLS User's Guide.
当您连接到不匹配 $DB_LOCALE 环境变量值的数据库时，dbaccess 实用程序将发出此消息。有关更多信息，请参见 GBase 8s GLS 用户指南中有关执行代码集转换的部分。